Checks for rules about Responsible Project - #27
Merged
Conversation
…esting_agent.ttl' more robust.
douglowe
commented
Oct 28, 2025
douglowe
commented
Oct 28, 2025
elichad
reviewed
Oct 29, 2025
elichad
left a comment
elichad
left a comment
There was a problem hiding this comment.
See also #15 (comment) and #15 (comment)
elichad
reviewed
Oct 29, 2025
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a replacement to PR #15 - with the relevant changes re-sat on top of the develop branch commits.
Rules implemented
Note
In what follows:
Responsible Project = entity (of type
schema:Project) referenced byschema:sourceOrganizationon thero-crate:RootDataEntity.Requesting Agent = entity (of type
schema:Person) referenced byschema:agentof aschema:CreateAction.Note that there may be multiple Responsible Projects and multiple Requesting Agents in a ro-crate.
Rules description
ro-crate:RootDataEntityMUST have theschema:sourceOrganizationpropertysh:Violationro-crate:RootDataEntity→schema:sourceOrganizationMUST point to entity/entities of typeschema:Projectsh:Violationschema:memberOfpropertysh:Warningschema:memberOfMUST point to entity/entities of typeschema:Projectsh:Violationschema:memberOfproperty, at least one of the Projects referenced by that property MUST also be referenced byRootDataEntity → schema:sourceOrganizationsh:Violationschema:fundingsh:Infoschema:fundingMUST reference entities of typeschema:Grantsh:Violationshema:membersh:Infoschema:memberMUST reference entities of typeschema:Organizationsh:Violationschema:memberSHOULD be among the entities referenced by each Requesting Agent →schema:affiliationif such properties exist.sh:WarningRules Not implemented
The following rules have not be implemented, and they may required manual validation. The rules description need rewording to improve clarity, and single entries may need to be split in different rules.
schema:nameof a Responsible Project SHOULD be descriptive, including the TRE-specific context (e.g. “TRE72 project 81”)sh:Warningschema:identifier. This MAY be an arraysh:Warningschema:identifieris not globally unique, include as aPropertyValueentity with a repository-specific name and valuesh:Infoschema:identifierMAY include multiplePropertyValueidentifiers for different TREs "sh:Info